# | Chapter | |
---|---|---|
1. | Payment Response Re–Try Queue API | |
2. | System Architecture and API | |
3. | User Experience | |
3.1 | - Customer Flow | |
3.2 | - Initial payment for customer | |
3.3 | - Capturing a Saved Card Detail | |
3.4 | - Customer Saved Cards UI | |
3.5 | - Deleting Saved Cards | |
4 | - Integration |
# | Tables |
---|---|
2.1 | Table 2: Merchant Prerequisites |
2.2 | Table 3: Save Card Mandatory Fields |
# | Figures |
---|---|
3.1 | Figure 1: Allow Save Customer Card Details |
3.3 | Figure 2: VPS.CardVault System Architecture |
3.2 | Figure 3: User Flow Save Card Details |
3.3 | Figure 4: Initial payment page |
3.4 | Figure 5: Save Card Details |
3.5 | Figure 6: Customer Saved Card List |
3.6 | Figure 7: Deleting a Saved Card |
3.7 | Figure 8: Confirmation of Saved Card Deletion for a card with an Alias |
3.8 | Figure 9: Confirmation of Saved Card Delete for a Card with no Alias |
Revision | Document | Description |
---|---|---|
2.51 | Recurring Payments Confluence / Web |
A service to ecommerce merchants for performing Scheduled Transaction Payments on the payment gateway at a recurring interval determined by the merchant. |
3.3.91 | Payments Page Confluence / Web |
This document presents a guide for merchants wishing to make use of the Vodacom Financial Services Payment Gateway recurring transaction processing service for eCommerce transactions via credit card. |
1.21 | Payment Broker Confluence / Web |
The Payments Broker will facilitate the creation of an encoded URL that will act as an intermediary between the customer and the Payment Gateway payment page. The merchant then makes this URL available to their customer. |
1.1 | Save Card Confluence |
Save card details allows merchants to pass their unique merchant Id and customer Id and have their customers previously saved card automatically display as a payment option on the payment page. |
1.2 | Payment Response Re-Retry Confluence |
The queuing mechanism implemented on the Payment Gateway to retry responses to merchants on the outcome of a payment request, in order to guarantee the delivery of that response. |